CVE-2026-9966
Google Chrome XML Integer Overflow Sandbox Escape
Description
Integer overflow in XML in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
INFO
Published Date :
May 28, 2026, 11:16 p.m.
Last Modified :
May 29, 2026, 8:28 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-9966
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 134c704f-9b21-4f2e-91b3-4a467353bcc0 |
Solution
- Update Google Chrome to the latest version.
- Ensure the browser is updated to 148.0.7778.216 or higher.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-9966.
| URL | Resource |
|---|---|
| https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html | Release Notes |
| https://issues.chromium.org/issues/506388321 | Permissions Required |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-9966 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-9966
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-9966 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-9966 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
May. 29, 2026
Action Type Old Value New Value Added CPE Configuration AND OR *cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* versions up to (excluding) 148.0.7778.216 OR cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:* Added Reference Type Chrome: https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html Types: Release Notes Added Reference Type Chrome: https://issues.chromium.org/issues/506388321 Types: Permissions Required -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
May. 29, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H -
New CVE Received by [email protected]
May. 28, 2026
Action Type Old Value New Value Added Description Integer overflow in XML in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High) Added CWE CWE-472 Added Reference https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html Added Reference https://issues.chromium.org/issues/506388321